Skip to content

[trello.com/c/aIVBEdjR] Improve coin tx sending algorithm #867

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: release/3.11.0
Choose a base branch
from

Conversation

Lainaaa
Copy link
Collaborator

@Lainaaa Lainaaa commented May 21, 2025

No description provided.

@Lainaaa Lainaaa requested a review from vovameister May 21, 2025 14:00
@Lainaaa Lainaaa self-assigned this May 26, 2025
@Lainaaa Lainaaa changed the title [trello.com/c/SL4zLZnb] Improve coin tx sending algorithm [trello.com/c/aIVBEdjR] Improve coin tx sending algorithm May 26, 2025
@Lainaaa Lainaaa marked this pull request as ready for review May 27, 2025 18:10
@@ -27,15 +27,14 @@ struct BTCRawTransaction {

func asBtcTransaction<T: BaseBtcTransaction>(_ as: T.Type, for address: String, blockId: String? = nil) -> T {
// MARK: Known values
let confirmationsValue: String?
let transactionStatus: TransactionStatus
var confirmationsValue: String? = nil
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

= nil - unnecessary change

@@ -44,6 +44,8 @@ extension BtcWalletService {
transaction: CoinTransaction,
btcTransaction: BtcTransaction
) async -> TransactionStatus {
// Before we already stored another status in RawBtcTransactionResponse.asBtcTransaction(_:for:height:).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the point of your comment if you haven't changed anything in this method

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants